Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1451

reference: 433-tree-1
name: 1451
tree-preservation-order: undefined
433-tpo-1
uprn
address-text
point: POINT (-1.040602 50.897692)
geometry: MULTIPOLYGON (((-1.040573 50.897689,-1.040575 50.897695,-1.040579 50.897700,-1.040585 50.897704,-1.040601 50.897707,-1.040610 50.897707,-1.040625 50.897700,-1.040629 50.897695,-1.040630 50.897690,-1.040629 50.897684,-1.040625 50.897679,-1.040611 50.897672,-1.040602 50.897671,-1.040593 50.897672,-1.040585 50.897675,-1.040579 50.897679,-1.040573 50.897689)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL